Subject: proposed agenda:Review and Comment

From: [email-masked]
Date: Tue, 21 Sep 93 01:46:11 PDT

1.	Meeting time(s)
The DLSw SIG is scheduled to meet during the September 1993 
AIW on Tuesday afternoon at 1:30-5:30.  If we need the time, 
our rooms are also available to resume after dinner from 
6:30-9:30.

We have a wrap-up meeting scheduled for Wednesday 5:45-6:30.  
The wrap-up meeting is for the SIG-as-a-whole to approve (or 
decline) proposals passed by the technical working groups the 
previous day.  This wrap-up meeting should be very short the 
proposals will either be approved quickly or sent back to the 
group without further debate.

2.	You have received the proposed charter as a separate 
message.  Please bring up disagreements on the network as 
soon as possible, specifying the number and letter of the 
disputed piece.  Merely disagreeing is not useful.  A 
specific, clearly-worded alternate clause is the appropriate 
format for reply.  This alternative clause may or may not be 
accompanied by supporting points of debate.

example:
     proposed charter clause:
         1.a.  All attendees should wear white socks.

     alternate clause:
        1.a.  Attendees must wear socks or stockings, but may 
wear any color of sock or stocking.

     reasons:
         1.  For reasons of religious persuasion or corporate 
             dress code, attendees may not be able to wear white socks or 
             stockings.
         2.  The use of foot coverings in addition to shoes, 
            however, contributes directly to the smoth working of the group.

3.	Meeting agenda - general

	a.	We will meet first as an entire group.  BE ON TIME!
		1:30-2:00	The SIG will discuss the charter, 
				milestones, and other necessary administrative 
				points.
		2:00-2:30	Each technical working group coordinator
				will briefly (with 1 overhead and in less
				than 5 minutes) update the group on the
				topics and proposals under consideration 
				by that group.
	
	b.	2:30-5:30	We will break into at least four technical
		working groups: connect, loop prevention, capabilities,   
		and flow control.  We have four rooms for them, each 
		with microphone, overheads, and writing pads/easels.
		The other three groups (priority/COS, MIB, and 
		conformance) may also meet, if there is more interest 
		than has been so far expressed on the Internet.

		There are three options for tracking these technical
		groups. The format will be decided by the SIG members.  
		Please read these options and reply as soon as possible. 
		Let us know also which tracks you would attend if any of 
		either proposal 1 or 2 is chosen.
			
	Proposal 1:  Four concurrent tracks
		Each of the four technical working groups would meet 
		for the entire three hours in separate rooms.  Each of these
		groups may decide to continue its work after dinner.

	Proposal 2:  Two concurrent tracks
		Two technical working groups will each meet for 1.5 hours. 
		These groups will then break and two other groups will
		meet for 1.5 hours.  (Recommended:  first two:  connect
		and flow-control, second two:  capabilities and loop 
		prevention.)  Each of these groups may decide to continue
		its work after dinner.

	Proposal 3:  No concurrent tracks
		The SIG will continue to meet as a whole, but will focus
		on the work of only one group each, for only 45 minutes.  
		The SIG as a whole may decide to continue work related to
		one or more of these groups after dinner.

3.	Meeting agenda - specific technical working groups
	Note:  These are still preliminary agendas:  additional 
written proposals may be available before or at the meeting.
	
	a.	Connect/Disconnect:  Alan Bartky

There will not be any specific written proposals.  Items to 
be discussed will be announced shortly. One basic 
disagreement must be ironed out before work can proceed.  

	b.	Capabilities:  Wayne Clark

Items we want to achieve consensus on:
(1) Shall DLSw be broken up into a base set + option sets?
(2) What features comprise the base set?
(3) What features comprise the option sets?
(4) Should a vendor id be included in the capabilities exchange?
(5) Should the capabilities exchange be carried over TCP or over UDP?
(6) Is it desirable to have a directory server / name server?
(7) Should CANUREACH / ICANREACH be optional?

Proposals on the table will be:
(1) Format of the capabilities exchange
(2) The finite state machine for exchange of capabilities.

	c.	Loop Prevention:  Choon Lee

o Introduction and problem description
o Is there consensus for not using spanning tree?
o Non spanning tree method proposals:
	- "heartbeat" method 
	- alternate method "modified TEST packets"
o General discussions, Q & A
o Next steps

	d.	Flow Control:  Shannon Nix

o Distribution of Technical Contributions
o Intro and Agenda	Shannon Nix, Netlink
o Presentation Technical Contributions
     - An Adaptive Pacing Proposal, Peter Gayek, IBM
     - Alternate TC Management Stategies, Anand Subramamniam,
      Novell
     - Alternate Buffer Allocation Stategy,Shannon Nix, 
      Netlink
o General Discussion, Q&A and Consensus-Building
o Formulate Stategy to Further Advance the Work

ACTION ITEMS (summary):

1.	Review and comment on proposed charter.

2.	Review and note preferred working group track proposal: 
_____four   _____two     _____none

3.	Note which track(s) you would attend if proposal 1 (four 
tracks) or proposal 2 (two tracks) is chosen:

If I can attend only ONE of these four, I would choose:
___loop prevention      ___capabilities      
___connect              ___flow control

If I can attend only TWO of the four, I would choose:
Track 1:  ______connect        or     ____flow-control
Track 2:  ______capabilities   or     ____loop prevention

3.	Comment on proposed technical group agendas.

---

From: Bernard Brady <[email-masked]>
Date: Tue, 21 Sep 93 09:07:51 EDT

ACTION ITEMS (summary):

2.	Review and note preferred working group track proposal: 
_____four   _XXX_two     _____none

If I can attend only ONE of these four, I would choose: 
	___loop prevention         ___capabilities
       ___connect                  XXX_flow control

If I can attend only TWO of the four, I would choose: 
Track 1:  XXX__connect       and  _XXX___flow-control  
Track 2:  ______capabilities   or     ____loop prevention